Expand description
Process Subplot input files.
Capture and communicate acceptance criteria for software and systems, and how they are verified, in a way that’s understood by all project stakeholders.
Modules§
- A representation of HTML using Rust types.
- A parsed Markdown document.
- Parse markdown into an HTML representation.
- Resources for subplot.
- Store information needed to build a table of contents for a document.
- Typeset various data types into HTML.
Structs§
- A binding of a scenario step to its implementation.
- Set of all known bindings.
- A parsed Subplot document.
- A code block with Dot markup.
- A data file embedded in the document.
- A collection of data files embedded in document.
- A scenario that has all of its steps matched with steps using bindings.
- A matched binding and scenario step, with captured parts.
- A list of matched steps.
- Metadata of a document, as needed by Subplot.
- A code block with pikchr markup.
- A code block with PlantUML markup.
- An acceptance test scenario.
- A scenario step.
- The text of a part of a scenario step.
- Typesetting style configuration for documents.
- An SVG image.
- A template specification.
- A list of warnings.
- Document metadata.
Enums§
- Part of a scenario step, possibly captured by a pattern.
- The kind of scenario step we have: given, when, or then.
- Define all the kinds of errors any part of this crate can return.
- A warning, or non-fatal error.
Traits§
- A code block with markup for a diagram.
Functions§
- Generate code for one document.
- Generate a test program from a document, using a template spec.
- Get the base directory given the name of the markdown file.
- Load a
Document
from a file. - Load a
Document
from a file.